The “Override the preview image using the view with this name (select or type the case-sensitive view name)” allows
you to specify a view to use to create a new preview image. If this option is unselected (the default) the preview image
will be regenerated from the last view used to make it, retaining the same preview image as was originally in the file.
If this option is selected, and a view with the specified name can be found in the family, the preview image will be
recreated using the specified view. The list of choices for views to use comes from the currently open family, however
you may type in any view name you wish. Just remember that view names are case-sensitive.
The “Create new shared parameters file from all unique shared parameters found in families” option, if checked, will
create a new shared parameters file that will consist of all the unique shared parameters found in all the families that
are processed.
There are some limitations:
• The file to create must not exist. You will not be able to proceed until the name of a new file to create has been
specified.
• Some information, such as the descriptive tool-tip text for parameters, cannot be determined from the families
and as such will not be included in the resulting shared parameters file
• The file WILL NOT be generated if the resulting file would have included bad data, such as multiple parameters
with identical case-sensitive names but different GUIDs. In a case like that, the log will include the reason why
the file could not be generated.
The “Create Type catalog files” option, if checked, will create type catalog files next to the family files being saved.
NOTE: The type catalog files will NOT include built-in parameters, such as Manufacturer, Cost, etc. These are most
commonly seen in the Identity Data group.
If type catalog files exist, the new ones being generated will overwrite the old ones.
IMPORTANT: If you choose to “Delete the types in the families” be aware that once the types are removed from the
families, they are gone and cannot be used to regenerate type catalogs again in the future. For example, if you generate
type catalogs and delete the types from the families, then later add a parameter to the families and want to regenerate
the type catalogs, the old type catalogs will get overwritten with new ones that have no types in them.
If you leave the types in the families users can still benefit from this by only loading the desired types into the project
using the type selector dialog, thus keeping the project smaller and lighter and simpler to use than if all the types in the
family were loaded, which is what happens when not using type catalogs.
IMPORTANT: If you choose to “Delete the types in the families” be sure to test this process on some families with this
option turned OFF to ensure the type catalog files generated include all the data necessary. Once the types in the